Servers configuration

These settings are independently set for each IPS Server machine.

When there is more than one machine, use the tabs labelled by the machine names to select the required machine.

The purpose of these settings is:

• to control the allocation of resource-intensive processes to the different machines in a cluster, in particular so that machines with greater resources (CPU cores, memory) can be allocated a greater share of the processing load;
• for each machine, to control the relative allocation of resources to different categories of processes.

Workers settings (general)

Worker processes are maintained by IPS Server to perform resource-intensive operations. You can set the number of workers which can run concurrently on a server machine, and how these workers can be allocated to different processing categories.

To change a setting, type a new value into an input field. Use the red 'Reset' button to change the setting to its default value. You must click 'Save all changes' at the top of the page to save the changes that you make.

Number of workers: You can set the maximum number of workers which can run concurrently on a server machine. The default number is 4.

Worker allocation strategy: This setting determines the number of workers that can be assigned to a single instance of an operation on the server (in previous versions only one worker could be allocated per operation per server). All strategies will be constrained by the number of workers requested as well as the number of available workers for the given category pool. The default strategy is Standard. Available strategies: Standard (allocate one available worker), Moderate (allocate half of the available workers), or Aggressive (allocate all of the available workers). Note: the allocation strategy is currently only applied to Result Set calculation jobs.

Processing category settings

The following are the processing categories that can be controlled:

• Dataflow Bulk Load
• PalantirCASH Result Set Calculation
• PalantirFINANCIALS Result Set Calculation
• PlanningSpace Decline Database Load
• PlanningSpace Decline File Load
• PlanningSpace Economics Result Set Calculation
• PlanningSpace Financials Result Set Calculation
• PlanningSpace Reconciliation Creation and Loading
• PlanningSpace Report Generation

Workers per processing category

You can set the maximum number of workers that can be simultaneously allocated to a processing category. The default number is 2.

Processor affinity per processing category

You can control which server CPU cores are usable by worker processes for each processing category. The default configuration is to make three-quarters of the cores usable, and to reserve one-quarter of the cores so that background jobs don’t impede other IPS functions or general processes of the server operating system. (At least one core will always be reserved, and rounding down will be used if the total number of cores is not divisible by 4.) The lowest-numbered cores will be reserved by default (i.e., starting from 'CPU0').

Note: If you modify the number of cores inside a server machine the process affinity settings will not automatically adjust to the change (for example, the machine initially has 8 cores and by default 'CPU3' to 'CPU7' have been set as checked; the number of cores is expanded to 16 and then the new cores - 'CPU8' to 'CPU 15' - will not be checked for process use although the previous settings for 'CPU3' to 'CPU7' will be preserved). You will need to manually set the process affinities or use the Reset buttons to re-apply the default allocation (for example, to have 12 out of 16 cores checked).

Scheduler thread pool settings

Type a new value for a setting into the input field.

Use the red 'Reset' button to change the setting to its default value.

You must click 'Save all changes' at the top of the page to save the changes that you make.

Setting name	Description	Default Value	Allowed values or range
Server Tasks Pool Size	The maximum number of threads that can be allocated to server tasks on a server machine.	48	0 to 2147483647
Periodic Tasks Pool Size	The maximum number of threads that can be allocated to periodic tasks on a server machine.	24	0 to 2147483647

Application processor affinity

You can separately control which server CPU cores are usable by each of the Planning Space (and CX Suite) applications, and some paticular application sub-processes (modules).

The default configuration is to make three-quarters of the cores usable, and to exclude one-quarter of the cores so that application processes (including background jobs) don’t impede the running of basic IPS functions. At least one core will be excluded, and rounding down will be used if the total number of cores is not divisible by 4. The lowest-numbered cores will be excluded by default (i.e., starting from 'CPU0').

Advanced settings

Use the 'Edit' button to change a setting value.

Use the red 'Reset' button to change the setting to its default value.

You must click 'Save all changes' at the top of the page to save the changes that you make.

Setting name	Description	Default Value	Allowed values or range
Category: Diagnostics
LogFolder	Folder that will contain the PlanningSpace log files for the server machine.	C:\ProgramData\Palantir\PalantirIPS 16.5\Logs	Any existing local file folder
DumpFolder	Folder that will contain the memory dump file in the event of unexpected shutdown of the IPS Server machine.	C:\ProgramData\Palantir\PalantirIPS 16.5\Dump	Any existing local file folder
Category: Scheduler
Check-in Interval	Sets the frequency (in milliseconds) at which each server machine in a cluster performs a check-in with other machines in the cluster. [Added in Version 16.5 Update 13]	30000	7500 to 3600000
Max Concurrent Tasks Per Job	Jobs use parallel tasks for some operations; this setting is the maximum allowed number of parallel tasks.	(Number of cores) - 1	Integer, 1 to 2*Default (depending on the number of machine processor cores)
Category: Web Server
Web Request Processor Affinity	The processor affinity setting determines which CPU cores will be assigned when an application-specific web request is received, such as OData and Web API requests; the server must be restarted after changing the setting for the setting to take effect. See Integration Services (OData) for explanation.	Depends on the number of machine CPU cores. Default value is '0x2' for 2 cores, '0xE' for 4 cores, '0xFC' for 8 cores, '0xFFF0' for 16 cores.	Hexadecimal value. See Integration Services (OData) for explanation.